Create shortcut icons on the toolbars to provide easy access to the most frequently used commands.

If you are designing an application in 256 colors, it's a good idea to make sure all your graphics are remapped to the same 256 color palette. Otherwise, you might notice palette changes as you move from frame to frame.

Give each object a clear and descriptive name that indicates what the object is used for. This will make life easier when you return to an old application three months later. You won't have to wonder what the object is for and why you used it. 

To gain more control over samples and how they are played, try using the MCI object. This allows you to track, pause, play and repeat samples with more control. Because MCI loads samples into an alias you can load samples straight from disk, thus decreasing your application size.

When designing an application that relies on small text or dots to show information, it's a good idea to avoid using colors, such as green and red, that some people have trouble seeing.

Whenever possible, use the memory options "load on call" and "destroy after use" for active objects. In the event editor, use the "create object" action to display your object. This reduces the time it takes to load your application since all graphics won't be loaded at the same time.

When developing an application that must handle many external files, a good file structure is particularly important.

After a major change it's a good idea to save your application with a new name. Then, if you wish to go back to a earlier version you can.

Comment your event lines. This makes it easy for you to understand your code when you look at it in the future. It also helps others to understand what you have done.

Use groups in the Event Editor to keep related events together.

If you want a group of events to be easily portable, store them in a related object's behavior.

If you have a group of events that are used in every frame, add them to the Global Events in the Application Properties.

To avoid making your applications over-complicated, try breaking them up into smaller logical groups in the Event Editor. Multiple CCA files can be inserted into the Storyboard editor.

Don't be afraid to try different approaches when solving problems. Not many people can write a complicated application that works the first time. There are usually many ways to write an application in Multimedia Fusion and with a little experience you will find the methods that work best for you.

If you have many active objects that do the same thing or interact with other objects in the same way, try using "object qualifier" to logically group them.

To copy a whole frame from one application that has multiple frames to another, you can open both applications and drag the frame from one Project Explorer to the other.

When you're making coffee (programmers like coffee at four in the morning), make mine white with one sugar.

If you are designing an application for Internet use, try to keep it as small as possible by lowering your sample rates. For example, instead of using16-bit stereo samples try using 8-bit mono samples.

You don't need to confirm every application change.  Go to the 'File' menu, select 'Preferences' and then choose the 'Picture / Animation Editor tab'.  You can set the auto-save options to automatically save all your changes.

Toolbars are completely customizable.  Not only can you change their positions, you can even change the order of the icons themselves.  You'll be spending many hours editing programs, so why not configure the editors to suit your own personal needs.

It's a good idea to name your application, frames and objects as soon as you create them. You might forget to do this later, and good descriptive labels can often speed up development.

Before switching to the Event Editor to implement code, make sure you have all the objects you need, not only for the immediate task, but for code you plan to implement in the near future. It will save you time if the objects you need are available and don't have to be created.

Global Values are a precious commodity.  As the only constant array of values, use them only when it is absolutely necessary. 

If your application needs to store a lot of global data and you've run out of Global values, try using the Array object. The array data can be written to a file and read in any frame.

To speed up imports, you can import graphics from the Windows desktop directly into the various editors of IMSI Multimedia Fusion. Try opening the Frame editor and dragging in a graphic file from Windows Explorer or the desktop.

Explore the new Event List Editor, which combines the power of the Event Editor, with a descriptive layout of the code. Your code can now be read, printed out and shared as easily as conventional programming scripts.

Don't panic!

To avoid a cluttered development environment, close all windows that you're not using. For example, don't leave properties windows open unless you're modifying one of the properties. Try to leave only the Project Explorer, and Frame and Event editors open.

